QuickChip w/ PreRead Feature with PreReadID

Overview

In addition to QuickChip five fields, an enhancement introduced a new PreReadID in response for QuickChip w/ PreRead. The PreReadID is configurable i.e. True/False. This unique ID identifies the pre-read data so it can be associated with a subsequent QuickChip transaction.

Default configured value for PreReadID is 'False', pre-read will return a PreReadID and that PreReadID is not required to be sent by the POS Application in the QuickChip portion of the transaction to be successful.
If PreReadID field is True, pre-read will return a PreReadID and that PreReadID should be sent by the POS Application in the QuickChip portion of the transaction to be successful.

Implementation

There are two "new" fields introduced for PreReadId, one for configuration and one for transaction flow operation. The configuration fields are per merchant in triPOS Direct. They are "checkForPreReadId", indicating that the feature/functionality is enabled/disabled and "preReadId", indicating unique ID, required for the QuickChip portion of the transaction to be successful.

The "new" transaction flow operation fields are per transaction for any of the particular endpoints supported, keeping in mind that for QuickChip, any endpoint transaction is a two-request process, one endpoint request for the PreRead stage immediately followed by the same endpoint request for the QuickChip stage. They are, "preRead" set to true to indicate the request is for PreRead, "checkForPreReadId", indicating that the feature/functionality is enabled/disabled, and "quickChip" set to true to indicate the request is for QuickChip (finalization),and "preReadId" unique ID generated in the first step response, and "provisionalAmount", an optional field, used to trigger CVM behavior (PIN/Signature, etc…) when above CVM limit for various card brands. If this field is not specified, it defaults to $1.00.. The two fields, "preRead" and "quickChip", should be mutually exclusive (i.e. - only one should be provided or set to true per request). Please note that the final amount should be provided at the final (QuickChip request) stage.

Example

1st request (Pre-Read).

{
  "laneId": "3",
  "preRead": true,
  "checkForPreReadId": true,
  "configuration": {
    "provisionalAmount": 30.00
  }
}

1st response(Pre-Read)

{
  "terminalId": "0047",
  "totalAmount": 0.0,
  "preReadId": "d2b791b2fd3d4bd5960217d5ac39df75",
  "approvalNumber": " ",
  "isApproved":true
  }
}

2nd request (QuickChip).

{
  "laneId": "3",
  "quickChip": true,
  "preReadId": "d2b791b2fd3d4bd5960217d5ac39df75",
  "transactionAmount": 7.31,
  "configuration": {
    "checkForDuplicateTransactions": false
  }
}

triPOS^®